Skip to content

fix: Remove Gmail specific CHECK response check#2

Merged
PineappleEmperor merged 1 commit intoPineappleEmperor:mainfrom
bbrks:fix_imap_check_response
May 16, 2025
Merged

fix: Remove Gmail specific CHECK response check#2
PineappleEmperor merged 1 commit intoPineappleEmperor:mainfrom
bbrks:fix_imap_check_response

Conversation

@bbrks
Copy link
Contributor

@bbrks bbrks commented May 13, 2025

Fixes #1

RFC 3501 does not specify what data is returned in response to a CHECK, and it appears that IMAP server implementations vary:

  • Gmail returns 'Success'
  • Fastmail returns 'Completed'

Remove the check for data and assume the response type 'OK' is enough.

RFC 3501 does not specify what data is returned in response to a CHECK,
and it appears that IMAP server implementations vary:

- Gmail returns 'Success'
- Fastmail returns 'Completed'

Remove the check for data and assume the response type 'OK' is enough.
@bbrks bbrks changed the title Remove Gmail specific CHECK response check fix: Remove Gmail specific CHECK response check May 13, 2025
@PineappleEmperor PineappleEmperor added the bug Something isn't working label May 16, 2025
@PineappleEmperor PineappleEmperor merged commit d00474b into PineappleEmperor:main May 16, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Setup: IMAP check does not support Fastmail

2 participants